-
-
Notifications
You must be signed in to change notification settings - Fork 16
Update antibodyregistry to use API #373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #373 +/- ##
=======================================
Coverage ? 53.04%
=======================================
Files ? 176
Lines ? 11821
Branches ? 1834
=======================================
Hits ? 6271
Misses ? 5312
Partials ? 238 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I know there are things to fix in terms of tests and formatting, which I will get back to, but I'm happy to get feedback on the implementation at this point. |
Co-authored-by: Mike Anselmi <[email protected]>
|
OK, I keep getting after about an hour when trying to get the full data. I might want to add some retry logic and/or caching of parts. |
Summary
Resolves #369.
This PR updates antibodyregistry to use their API. The API requires login, which is now handled by
httpx. After a login sequence that uses personal login information, the API can be used to download all the data.The previous implementation of this API was broken by updates from the maintainers of the data.
Issue: Slow Download
The current implementation takes ~3 hours. We should consider running concurrent requests to speed this up if 3 hours is unacceptable.